Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NMS-16486: Extracted caches from DocumentEnricherImpl #7397

Merged
merged 6 commits into from
Aug 30, 2024

Conversation

christianpape
Copy link
Contributor

Copy link
Member

@indigo423 indigo423 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Beside the comment, nothing I can complain about :)

http://aries.apache.org/schemas/blueprint-ext/blueprint-ext-1.1.xsd
">
<!-- Configuration properties -->
<cm:property-placeholder id="cacheConfigProperties" persistent-id="org.opennms.features.telemetry.protocols.common" update-strategy="reload">
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it makes sense to create a documentation enhancement to add all these new configuration properties to the docs and make it a requirement when we decide to merge this into an official release. It's not a blocker for the merge into NMS-16375.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch. Yes, we have to add these to the docs.

Copy link
Member

@fooker fooker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Main itch is the naming. The NodeMetadataCache gives out NodeInfo. Also the package naming does not reflect the maven project structure. NodeInfo is located in .../protocols/common/cache where as protocols/common and protocols/cache both exist.

@christianpape
Copy link
Contributor Author

Main itch is the naming. The NodeMetadataCache gives out NodeInfo. Also the package naming does not reflect the maven project structure. NodeInfo is located in .../protocols/common/cache where as protocols/common and protocols/cache both exist.

Yes, you are totally right. The common.cache is a leftover of changes I reverted. I'll fix that.

Copy link
Member

@indigo423 indigo423 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@christianpape christianpape force-pushed the jira/NMS-16486 branch 2 times, most recently from a6e7326 to 16a33b7 Compare August 29, 2024 12:11
@christianpape christianpape merged commit 7ab8b5f into jira/NMS-16375 Aug 30, 2024
21 checks passed
@christianpape christianpape deleted the jira/NMS-16486 branch August 30, 2024 06:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants